Acts on the maintainer decision that leadforge becomes a platform hosting two
PARALLEL, peer generation schemes (lead_scoring + lifecycle), not a
lead-scoring framework with an LTV bolt-on.

design.md:
- New §2.5 "peer generation schemes": decisions D10 (extract the
  GenerationScheme abstraction EARLY, against the known-good lead-scoring path,
  output byte-identical) and D11 (physically reorganize into
  leadforge/schemes/{lead_scoring,lifecycle}/ now). Adds the scheme→recipe→
  bundle hierarchy, the GenerationScheme protocol shape, a shared-envelope vs
  per-scheme table, the target package layout, reorg safety rails for the
  published 1.x package, and a note that LTV-Pb (#104) already aligns.
- §10 inventory: lifecycle modules now live under schemes/lifecycle/; adds
  schemes/base.py; recipe declares scheme: lifecycle.

roadmap.md (reshaped to 9 milestones / ~18 PRs, Pa..Pr):
- New LTV-M2 "Generation-scheme architecture + physical reorg" (LTV-Pd/Pe/Pf):
  protocol+registry against lead-scoring → move lead-scoring into
  schemes/lead_scoring/ → scaffold schemes/lifecycle/ and relocate the
  LTV-Pb/Pc specs.
- Lifecycle build milestones (population/engine/snapshots) renumbered to
  M3-M5 and now land directly under schemes/lifecycle/.
- LTV-M6 registers LifecycleScheme end-to-end + recipe + manifest
  generation_scheme + schema v6.

.agent-plan.md: scheme-architecture summary + revised status (M2 next; can run
in parallel with M1 since it only touches the existing lead-scoring path).

Stacked on the LTV-Pb branch (#104) because it references that work as done.
No package code in this PR.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Acts on the maintainer decision that leadforge becomes a platform hosting two
PARALLEL, peer generation schemes (lead_scoring + lifecycle), not a
lead-scoring framework with an LTV bolt-on.

design.md:
- New §2.5 "peer generation schemes": decisions D10 (extract the
  GenerationScheme abstraction EARLY, against the known-good lead-scoring path,
  output byte-identical) and D11 (physically reorganize into
  leadforge/schemes/{lead_scoring,lifecycle}/ now). Adds the scheme→recipe→
  bundle hierarchy, the GenerationScheme protocol shape, a shared-envelope vs
  per-scheme table, the target package layout, reorg safety rails for the
  published 1.x package, and a note that LTV-Pb (#104) already aligns.
- §10 inventory: lifecycle modules now live under schemes/lifecycle/; adds
  schemes/base.py; recipe declares scheme: lifecycle.

roadmap.md (reshaped to 9 milestones / ~18 PRs, Pa..Pr):
- New LTV-M2 "Generation-scheme architecture + physical reorg" (LTV-Pd/Pe/Pf):
  protocol+registry against lead-scoring → move lead-scoring into
  schemes/lead_scoring/ → scaffold schemes/lifecycle/ and relocate the
  LTV-Pb/Pc specs.
- Lifecycle build milestones (population/engine/snapshots) renumbered to
  M3-M5 and now land directly under schemes/lifecycle/.
- LTV-M6 registers LifecycleScheme end-to-end + recipe + manifest
  generation_scheme + schema v6.

.agent-plan.md: scheme-architecture summary + revised status (M2 next; can run
in parallel with M1 since it only touches the existing lead-scoring path).

Stacked on the LTV-Pb branch (#104) because it references that work as done.
No package code in this PR.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

…leScheme [LTV-Pg.1] (#111)

* refactor(schema): scaffold schemes/lifecycle/ + register stub LifecycleScheme [LTV-Pg.1]

First half of the schema reorg (LTV-Pg). Gives the lifecycle scheme its own
home and makes it a registered peer of lead_scoring, ahead of building its
pipeline (M3–M6). Byte-identical; lead-scoring catalog unchanged.

- New leadforge/schemes/lifecycle/ package:
  - entities.py — the 5 lifecycle rows (CustomerLifecycleRow,
    SubscriptionLifecycleRow, SubscriptionEventRow, HealthSignalRow, InvoiceRow)
    + LIFECYCLE_ROW_TYPES / LIFECYCLE_TABLE_NAMES, moved from schema/entities.py.
    AccountRow / EntityRowProtocol / _empty_df are shared and imported from
    leadforge.schema.entities.
  - relationships.py — LIFECYCLE_CONSTRAINTS, moved from schema/relationships.py
    (reuses the shared FKConstraint).
  - __init__.py — stub LifecycleScheme (build_world/write_bundle raise
    NotImplementedError until M3–M6); self-registers. schemes/__init__ imports it.
- schema/entities.py and schema/relationships.py: lifecycle definitions removed;
  breadcrumb comments point to the new home. ALL_ROW_TYPES / ALL_CONSTRAINTS
  unchanged.
- tests/schema/test_lifecycle_entities.py → tests/schemes/lifecycle/test_entities.py
  with updated imports; tests/schemes/test_registry.py gains lifecycle
  registration + stub-raises-NotImplementedError tests.
- CHANGELOG, CLAUDE.md (both layouts), roadmap (Pg split into Pg.1/Pg.2),
  agent-plan updated.

available_schemes() → ("lead_scoring", "lifecycle"). Verified byte-identical
(14/14 files); full suite 1534 passed / 51 skipped; ruff + mypy clean (92 files).

Note: class-level extraction from the shared schema/entities.py can't be a git
rename (multiple classes pulled from a multi-class file); the lifecycle rows
were only added in #104 so the history loss is shallow.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* docs(ltv): record LTV-Pg.1 (#111) in roadmap + agent-plan [LTV-Pg.1]

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* refactor(schema): make_empty_dataframe public (self-review) [LTV-Pg.1]

Self-review: schemes/lifecycle/entities.py imported a private symbol
(`_empty_df`) across packages — a leading-underscore name signals
module-internal, so importing it elsewhere is a smell. Promote it to a public
shared helper `make_empty_dataframe` in leadforge.schema.entities (used by both
the lead-scoring rows and the lifecycle rows); the cross-module import is now
legitimate.

No behaviour change (verified byte-identical, 14/14); full suite passes; ruff +
mypy clean. (When LTV-Pg.2 moves lead-scoring rows out of schema/entities.py,
make_empty_dataframe + EntityRowProtocol stay as the shared primitives.)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>